Multivalued dependency

In database theory, a multivalued dependency is a full constraint between two sets of attributes in a relation.

In contrast to the functional dependency, the multivalued dependency requires that certain tuples be present in a relation. Therefore, a multivalued dependency is a special case of tuple-generating dependency. The multivalued dependency plays a role in the 4NF database normalization.

A multivalued dependency is a special case of a join dependency, with only two sets of values involved, i.e. it is a binary join dependency.

A multivalued dependency exists when there are at least three attributes (like X,Y and Z) in a relation and for a value of X there is a well defined set of values of Y and a well defined set of values of Z. However, the set of values of Y is independent of set Z and vice versa.

Formal definition

The formal definition is as follows:^[1]

Let $R$ be a relation schema and let $\alpha \subseteq R$ and $\beta \subseteq R$ be sets of attributes. The multivalued dependency $\alpha \twoheadrightarrow \beta$ (" $\alpha$ multidetermines $\beta$ ") holds on $R$ if, for any legal relation $r(R)$ and all pairs of tuples $t_{1}$ and $t_{2}$ in $r$ such that $t_{1}[\alpha ]=t_{2}[\alpha ]$ , there exist tuples $t_{3}$ and $t_{4}$ in $r$ such that:

${\begin{matrix}t_{1}[\alpha ]=t_{2}[\alpha ]=t_{3}[\alpha ]=t_{4}[\alpha ]\\t_{1}[\beta ]=t_{3}[\beta ]\\t_{2}[\beta ]=t_{4}[\beta ]\\t_{1}[R\setminus (\alpha \cup \beta )]=t_{4}[R\setminus (\alpha \cup \beta )]\\t_{2}[R\setminus (\alpha \cup \beta )]=t_{3}[R\setminus (\alpha \cup \beta )]\end{matrix}}$

Informally, if one denotes by $(x,y,z)$ the tuple having values for $\alpha ,$ $\beta ,$ $R-\alpha -\beta$ collectively equal to $x,$ $y,$ $z$ , then whenever the tuples $(a,b,c)$ and $(a,d,e)$ exist in $r$ , the tuples $(a,b,e)$ and $(a,d,c)$ should also exist in $r$ .

The multivalued dependency can be schematically depicted as shown below:

${\begin{matrix}{\text{tuple}}&\alpha &\beta &R\setminus (\alpha \cup \beta )\\t_{1}&a_{1}..a_{n}&b_{1}..b_{m}&d_{1}..d_{k}\\t_{2}&a_{1}..a_{n}&c_{1}..c_{m}&e_{1}..e_{k}\\t_{3}&a_{1}..a_{n}&b_{1}..b_{m}&e_{1}..e_{k}\\t_{4}&a_{1}..a_{n}&c_{1}..c_{m}&d_{1}..d_{k}\end{matrix}}$

Example

Consider this example of a relation of university courses, the books recommended for the course, and the lecturers who will be teaching the course:

University courses
Course	Book	Lecturer
AHA	Silberschatz	John D
AHA	Nederpelt	John D
AHA	Silberschatz	William M
AHA	Nederpelt	William M
AHA	Silberschatz	Christian G
AHA	Nederpelt	Christian G
OSO	Silberschatz	John D
OSO	Silberschatz	William M

Because the lecturers attached to the course and the books attached to the course are independent of each other, this database design has a multivalued dependency; if we were to add a new book to the AHA course, we would have to add one record for each of the lecturers on that course, and vice versa.
Put formally, there are two multivalued dependencies in this relation: {course} $\twoheadrightarrow$ {book} and equivalently {course} $\twoheadrightarrow$ {lecturer}.
Databases with multivalued dependencies thus exhibit redundancy. In database normalization, fourth normal form requires that for every nontrivial multivalued dependency X $\twoheadrightarrow$ Y, X is a superkey. A multivalued dependency X $\twoheadrightarrow$ Y is trivial if Y is a subset of X, or if $X\cup Y$ is the whole set of attributes of the relation.

Properties

If $\alpha \twoheadrightarrow \beta$ , Then $\alpha \twoheadrightarrow R-\beta$
If $\alpha \twoheadrightarrow \beta$ and $\gamma \subseteq \delta$ , Then $\alpha \delta \twoheadrightarrow \beta \gamma$
If $\alpha \twoheadrightarrow \beta$ and $\beta \twoheadrightarrow \gamma$ , then $\alpha \twoheadrightarrow \gamma -\beta$

The following also involve functional dependencies:

If $\alpha \rightarrow \beta$ , then $\alpha \twoheadrightarrow \beta$
If $\alpha \twoheadrightarrow \beta$ and $\beta \rightarrow \gamma$ , then $\alpha \twoheadrightarrow \gamma -\beta$

The above rules are sound and complete.

A decomposition of R into (X, Y) and (X, R − Y) is a lossless-join decomposition if and only if X $\twoheadrightarrow$ Y holds in R.
Every FD is an MVD because if X $\rightarrow$ Y, then swapping Y's between tuples that agree on X doesn't create new tuples.
Splitting Doesn't Hold. Like FD's, we cannot generally split the left side of an MVD.But unlike FD's, we cannot split the right side either, sometimes you have to leave several attributes on the right side.
Closure of a set of MVDs is the set of all MVDs that can be inferred using the following rules (Armstrong's axioms):
- Complementation: If X $\twoheadrightarrow$ Y, then X $\twoheadrightarrow$ R - Y
- Augmentation: If X $\twoheadrightarrow$ Y and Z $\subseteq$ W, then XW $\twoheadrightarrow$ YZ
- Transitivity: If X $\twoheadrightarrow$ Y and Y $\twoheadrightarrow$ Z, then X $\twoheadrightarrow$ Z - Y
- Replication: If X $\rightarrow$ Y, then X $\twoheadrightarrow$ Y
- Coalescence: If X $\twoheadrightarrow$ Y and $\exists$ W s.t. W $\cap$ Y = $\emptyset$ , W $\rightarrow$ Z, and Z $\subseteq$ Y, then X $\rightarrow$ Z

Definitions

Full constraint: A constraint which expresses something about all attributes in a database. (In contrast to an embedded constraint.) That a multivalued dependency is a full constraint follows from its definition, as where it says something about the attributes $R-\beta$ .
Tuple-generating dependency: A dependency which explicitly requires certain tuples to be present in the relation.
Trivial multivalued dependency 1: A multivalued dependency which involves all the attributes of a relation i.e. $R=\alpha \cup \beta$ . A trivial multivalued dependency implies, for tuples $t_{1}$ and $t_{2}$ , tuples $t_{3}$ and $t_{4}$ which are equal to $t_{1}$ and $t_{2}$ .
Trivial multivalued dependency 2: A multivalued dependency for which $\beta \subseteq \alpha$ .